home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.20041116-20060924 / 000338_jaltman2@nyc.rr.com_Sat May 6 15:11:26 2006.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB

  1. Path: newsmaster.cc.columbia.edu!newsfeed.nyu.edu!news.maxwell.syr.edu!nx01.iad01.newshosting.com!newshosting.com!68.1.17.232.MISMATCH!peer01.cox.net!cox.net!cyclone1.gnilink.net!gnilink.net!news-feed-01.rdc-nyc.rr.com!news.rr.com!news-out.nyc.rr.com!news-wrt-01.rdc-nyc.rr.com.POSTED!53ab2750!not-for-mail
  2. From: Jeffrey Altman <jaltman2@nyc.rr.com>
  3. User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
  4. MIME-Version: 1.0
  5. Newsgroups: comp.protocols.kermit.misc
  6. Subject: Re: Another Secure FTP thread -- Protection Levels
  7. References: <1146861121.842424.256350@i40g2000cwc.googlegroups.com>
  8. In-Reply-To: <1146861121.842424.256350@i40g2000cwc.googlegroups.com>
  9. Content-Type: text/plain; charset=ISO-8859-1
  10. Content-Transfer-Encoding: 7bit
  11. Lines: 41
  12. Message-ID: <Q7P6g.35918$cY3.14015@news-wrt-01.rdc-nyc.rr.com>
  13. Date: Fri, 05 May 2006 21:06:56 GMT
  14. NNTP-Posting-Host: 68.175.91.105
  15. X-Complaints-To: abuse@rr.com
  16. X-Trace: news-wrt-01.rdc-nyc.rr.com 1146863216 68.175.91.105 (Fri, 05 May 2006 17:06:56 EDT)
  17. NNTP-Posting-Date: Fri, 05 May 2006 17:06:56 EDT
  18. Organization: Road Runner High Speed Online http://www.rr.com
  19. Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15595
  20.  
  21. C-Kermit does not allow the command channel to be reset to clear
  22. after it is protected by AUTH TLS.   This is simply not permitted.
  23.  
  24. Jeffrey Altman
  25.  
  26.  
  27. Ed Gage wrote:
  28. > Read through the other FTP thread -- very helpful.
  29. > The obstacle I'm dealing with is connecting to a secure FTP server
  30. > through our router.  I'm behind a Linksys router which for some reason
  31. > doesn't like to read encrypted packets.
  32. > Here's what I tried with a newly-compiled CKERMIT 8.12:
  33. > set ftp autoencryption off
  34. > set ftp authtype ssl
  35. > set ftp command-protection-level clear
  36. > ftp ###.###.###.### /user:##### /password:#####
  37. > It responds with:
  38. > Connected to ###.###.###.###
  39. > SSL accepted as authentication type
  40. > ....then the self-signed certificate issue discussed in the other
  41. > thread, but not a crisis at this time.
  42. > The issue is a SHOW FTP returning:
  43. > Available security methods:
  44. >  ftp authtype:                  SSL
  45. >  ftp auto-encryption:           off
  46. >  ftp credential-forwarding:     off
  47. >  ftp command-protection-level:  safe
  48. >  ftp data-protection-level:     private
  49. >  ftp secure proxy:              (not set)
  50. > How come when I set the command-protection-level to clear, it connects
  51. > as safe?  Is this dictated by the server?